電影票價 (2026-01)

This is my OpenCode setup for local models, mainly using a customized llama.cpp configuration.

For Qwen 3.8, DeepSeek V4, and Glimmer, the models are already trained to support reasoning effort levels. Depending on the model, these may be exposed as low, medium, high, xhigh, or as low, high, and max.

For models that support reasoning but were not trained with explicit reasoning-effort levels, such as the Qwen 3.5 and 3.6 variants, I use a token budget to limit the amount of reasoning.

Although Qwen 3.8 has built-in reasoning-effort levels, I still apply a maximum reasoning-token cap for each effort level.

Although the llama.cpp CLI flags specify preserve_thinking and a default reasoning budget, these can still be overridden through the API, so this works fine for my setup.

https://code-boxx.com/simple-php-webauthn/

1. Change $rp to your own in 3-init.php.
2. Run composer require lbuchs/webauthn to download the PHP Web Authn Library

Copyright by Code Boxx

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.